Point-to-point data communication implemented with multipoint network data communication components

ABSTRACT

A data communication system is configured to communicatively link a host device and a client device with a point-to-point data communication link, where the point-to-point data communication link is configured with multipoint network data communication components designed for data communication over a distributed network. A data communication interface at the host device is communicatively linked with a data communication interface driver via the point-to-point data communication link between the host device and the client device. The data communication interface driver communicates with a virtual driver component for the client device via a virtual network at the client device.

TECHNICAL FIELD

This invention relates to communicatively linking computing systems and,in particular, to implementing a point-to-point data communication linkbetween two computing devices with multipoint distributed network datacommunication components.

BACKGROUND

Computing devices can be communicatively linked with a point-to-pointcommunication connection to enable communication between a client deviceand a host device, for example. A client device might include a portablelaptop computer, a tablet PC, a handheld personal digital assistant(PDA), a cellular phone, and other similar devices that can beconfigured for direct communication with a host device for synchronizedfile updates and other data manipulation functions.

FIG. 1 illustrates a conventional point-to-point communication system100 that includes a host computing device 102 and a client device 104communicatively linked together with a point-to-point serial connection106. The host device 102 and the client device 104 each include anapplication layer 108 and 110, respectively. In this example,applications 108 and 110 can each be a synchronization applicationdesigned to facilitate data communication between the host device 102and the client device 104.

Typically, data communication between computing devices is divided intofunctional layers between a software application layer, such asapplication layer 108, and a communication link, such as thepoint-to-point serial connection 106. Each functional layer provides anappropriately formatted data transfer function to an adjacent functionallayer while abstracting the adjacent functional layer from thefunctional implementation details of a particular layer. Data transferbetween the functional communication layers is communicated from higherlayers to lower layers, and vice-versa, and by convention, anapplication layer is a higher layer that communicates information downto a lower layer, such as to a hardware connection interface and/ordriver. Accordingly, each functional layer manipulates and formats dataas it is communicated from one layer to the next, and reverses the datamanipulation and formatting for the data when it is communicated in anopposite direction.

Host computing device 102 includes a transport protocol layer 112 thatfacilitates information communication between application layer 108 andlower functional communication layers. Implementations of the transportprotocol layer 112 can include the Transmission ControlProtocol/Internet Protocol (TCP/IP) which is the basic communicationprotocol for the Internet. TCP/IP can also be used as a communicationsprotocol in a private network, such as an intranet or an extranet.TCP/IP is primarily designed for point-to-point communication, in thatcommunication is from one point, such as from host computing device 102,to another point, such as to client device 104. Point-to-pointcommunication is also commonly designated as “PPP”.

The transport protocol layer 112 communicates information to apoint-to-point protocol layer 114, which in turn communicates theinformation to a serial port 116 via a serial port interface 118 andserial port driver 120. The point-to-point protocol layer 114 uses theInternet protocol (IP) and is designed to facilitate informationcommunication between two computing devices via a serial interface. ThePPP protocol layer 114 provides the services of a data-link layer andpackages TCP/IP packets received from the transport protocol layer 112and forwards them to the serial port interface 118.

Client device 104 also includes a transport protocol layer 122 thatfacilitates information communication between application layer 110 anda point-to-point protocol layer 124. The PPP protocol layer 124communicates the information between the transport protocol layer 122and a serial port 126 via a serial port interface 130 and serial portdriver 132.

The serial port interface 118 and serial port driver 120 at the hostcomputing device 102 support the point-to-point serial connection 106between serial port 116 at host computing device 102 and serial port 126at client device 104. The serial connection 106 is one of the mostcommon communication links to implement between two devices. Serial portconnections, however, are relatively slow and typically communicateinformation at a rate of only 115 kilobits per second.

FIG. 2 illustrates a point-to-point communication system 200 thatincludes a host computing device 202 and a client device 204communicatively linked with a point-to-point universal serial bus (USB)connection 206. The USB connection 206 is preferable over the serialconnection 106 (FIG. 1) because USB supports a data transfer rate of 12megabits per second which accommodates connecting a wide range ofdevices to host computing device 202 at a higher data transfer rate.

Host computing device 202 and client device 204 each include anapplication layer 208 and 210, a transport protocol layer 212 and 214,and a point-to-point protocol layer 216 and 218, respectively. Each ofthese components are described above with reference to FIG. 1.

Host computing device 202 also includes a virtual serial port driver 220that communicates information between the point-to-point protocol layer216 and a USB port 222. The client device 204 also includes a virtualserial port driver 224 that communicates information between thepoint-to-point protocol layer 218 and a USB port 226. A virtual serialport driver is also commonly known as a USB serial host driver thatenables a point-to-point communication link between USB port 222 at hostcomputing device 202 and USB port 226 at client device 204. The virtualserial port driver 220 exposes a standard serial interface in the hostcomputing device 202 to the upper-level application 208 so that theapplication can communicate data via USB connection 206 as if it were astandard serial port connection.

FIG. 3 illustrates a multipoint data communication system 300 thatincludes a computing device 302 having multipoint distributed networkdata communication components. Computing device 302 includes anapplication layer 304 and a transport protocol layer 306. The transportprotocol layer 306 is described above with reference to FIG. 1. Theapplication 304 can be an Internet browser application, for example,that facilitates user interaction with the Internet 308 via a local areanetwork (LAN) 310.

Computing device 302 also includes multipoint network data communicationcomponents such as a Network Driver Interface Specification (NDIS) layer312 and a miniport driver layer 314. The NDIS layer 312 is a networkdevice driver communication protocol layer that specifies howcommunication protocol layers or programs, such as TCP/IP, and networkdevice drivers communicate with each other. The NDIS layer 312 providesa layer of abstraction for the development of network device drivers.The abstraction includes an application programming interface (API) tofunctionally identify the services provided by the NDIS layer 312without requiring that adjacent layers recognize the implementationdetails for the NDIS layer. This provides a device-independent formatfor commands and data that are communicated to a network-connecteddevice.

The NDIS layer 312 configures network-connected devices forcommunication to send and receive network data on behalf of applicationsexecuting on computing device 302. The applications, such as application304, communicate information to the NDIS layer 312 through a transportprotocol configured for the type of data exchanged and the underlyingnetwork used for transmission of the data, such as via TCP/IP, NetBEUI,NWLINK, or other similar communication protocol layers. The NDIS layer312 communicates with lower driver layers, such as the bus and/ornetwork interface 316, with NDIS object identifiers (OIDs) to performnetwork device configuration and data communication management of NDISdata packets.

The NDIS layer 312 supports basic types of network interface card (NIC)drivers which are also referred to as NDIS miniport drivers. Theminiport driver layer 314 communicates information with the NDIS layer312 and communicates with the bus and/or network interface 316 throughvendor-specific APIs. The bus and/or network interface 316 is typicallybus-specific or network-specific and communicates with network-connecteddevices through the appropriate bus or network interface. Typically, anNDIS miniport driver is specifically configured for a particularhardware device.

Both the NDIS miniport driver layer 314 and the bus and/or networkinterface 316 are configured by a manufacturer (OEM) of anetwork-connected device to communicate via vendor-specific APIs. Thus,the NDIS miniport driver layer 314 conforms to an NDIS layer API tocommunicate with NDIS layer 312, and the bus and/or network interface316 conforms to the appropriate bus or network interface to communicateinformation to a network-connected device, or multiple network-connecteddevices via the LAN 310.

FIG. 4 illustrates a multipoint data communication system 400 thatincludes a computing device 402 having multipoint distributed networkdata communication components. Computing device 402 includes anapplication layer 404 and a transport protocol layer 406. The transportprotocol layer 406 is described above with reference to FIG. 1.Application 404 can be a synchronization application, for example,designed to facilitate data communication between computing device 402and remote device 408. Application 404 also utilizes remote device 408to access a LAN 410.

Computing device 402 also includes an NDIS layer 412 and a Remote NDISminiport driver layer 414. The NDIS layer 412 is described above withreference to FIG. 3. In FIG. 4, the Remote NDIS architecture replacesthe NDIS miniport driver layer 314 and the bus and/or network interface316 of FIG. 3, both of which were provided by a network-connected devicemanufacturer, with a Remote NDIS miniport driver layer 414 and a busand/or network-specific microport 416. Each combination of componentsprovides the computing devices 302 and 402 access to a LAN 310 and 410respectively.

Remote NDIS miniport driver layer 414 and the bus and/ornetwork-specific microport 416 are independent of any particularnetwork-connected device 408 and can be included as part of thecomputing device 402 operating system similarly to the transportprotocol layer 406 and the NDIS protocol layer 412. With Remote NDIS,hardware manufacturers providing remote devices do not have to providehost-based drivers for their devices. Remote NDIS is the subject of U.S.patent application Ser. No. 09/302,735 entitled “Method and System forAbstracting Network Device Drivers”, the disclosure of which isincorporated by reference herein.

Remote NDIS miniport driver layer 414 defines a connection-independentmessage set along with a description of how the message set operatesover a particular connection, such as with a specific bus or network. ARemote NDIS interface is standardized to facilitate a defined set ofhost drivers to support any number of network-connected devices therebyeliminating the need to install new drivers to support a newly connectednetwork device.

The Remote NDIS miniport driver layer 414 encapsulates NDIS objectidentifiers (OIDs) and NDIS data packets into data structures known asRemote NDIS messages that can be communicated without modification to aremotely connected device 408. The Remote NDIS miniport driver layer 414communicates the Remote NDIS messages with the bus and/ornetwork-specific microport driver layer 416 which can include a USB busmicroport, a 1394 bus microport, a Bluetooth microport, or any othersimilar communication protocol microport.

The bus and/or network-specific microport driver layer 416 is anintermediate layer that interfaces with the specific bus or networkresponsible for communicating the Remote NDIS messages to the remotedevice 408. The microport driver layer 416 receives Remote NDIS messagesand communicates them to a corresponding element of the specific bus ornetwork driver layer. The Remote NDIS messages are communicated via theUSB connection to remote device 408.

With the Remote NDIS architecture, the network communication protocolmechanisms are abstracted above the bus and/or network-specificmicroport driver layer 416. Adding a new network-connected device can beaccomplished by changing or modifying only the Remote NDIS miniportdriver layer 414. The microport driver layer 416 remains unchangedbecause it is a message transport layer that passes NDIS layer OIDs andNDIS data packets encapsulated in Remote NDIS messages.

SUMMARY

A data communication system is configured to communicatively link a hostdevice and a client device with a point-to-point data communicationlink, where the point-to-point data communication link is configuredwith multipoint network data communication components designed for datacommunication over a distributed network. A data communication interfaceat the host device is communicatively linked with a data communicationinterface driver via the point-to-point data communication link betweenthe host device and the client device.

The data communication interface at the host device can be implementedwith the Remote Network Driver Interface Specification (NDIS), and thedata communication interface driver is a Remote NDIS driver. The RemoteNDIS component communicates Remote NDIS messages with the Remote NDISdriver via the point-to-point data communication link.

The data communication interface driver (e.g., Remote NDIS driver) atthe client device communicates with a virtual driver component for theclient device via a virtual network. The virtual network can beimplemented as a local area network (LAN) and the Remote NDIS drivercommunicates the Remote NDIS messages with the virtual driver componentvia the LAN.

The data communication system includes a connection interface to couplethe point-to-point data communication link with the client device. Theconnection interface can be implemented with a Universal Serial Bus datacommunication interface, a 1394 bus data communication interface, awireless data communication interface, a Bluetooth data communicationinterface, an infrared data communication interface, or other similarpoint-to-point data communication protocol interface.

BRIEF DESCRIPTION OF THE DRAWINGS

The same numbers are used throughout the drawings to reference likefeatures and components.

FIG. 1 is a block diagram that illustrates communicatively linking twocomputing devices with a conventional point-to-point serial connection.

FIG. 2 is a block diagram that illustrates communicatively linking twocomputing devices with a conventional point-to-point USB connection.

FIG. 3 is a block diagram that illustrates a computing device havingconventional multipoint distributed network data communicationcomponents.

FIG. 4 is a block diagram that illustrates a computing device havingconventional multipoint distributed network data communicationcomponents configured to communicatively link with network-connectedremote devices.

FIG. 5 is a block diagram that illustrates a point-to-point datacommunication link between two computing devices implemented withmultipoint distributed network data communication components.

FIG. 6 is a block diagram that illustrates point-to-point datacommunication links between a host computing device and multiple clientdevices, each configured with multipoint distributed network datacommunication components.

FIG. 7 is a flow diagram of a method for implementing a point-to-pointdata communication link between computing devices configured withmultipoint distributed network data communication components.

FIG. 8 is a diagram of computing systems, devices, and components in anenvironment that can be used to implement the invention describedherein.

DETAILED DESCRIPTION

Introduction

The following describes systems and methods for point-to-point datacommunication between computing devices implemented with distributednetwork communication components intended for multipoint datacommunication. The described point-to-point data communication systemutilizes the Network Driver Interface Specification (NDIS) and RemoteNDIS communication interface layers that are designed for multipointdata communication over a distributed network. Inherently, NDIS andRemote NDIS are not designed to facilitate point-to-point communicationbetween two computing devices. However, implementing a host computingdevice's Remote NDIS driver layer in an external client device can beutilized to establish a basic point-to-point data communication linkbetween the two computing devices.

The described point-to-point data communication system is versatile inthat a user can communicate with a host computing device configured withRemote NDIS via a point-to-point data communication link from anyportable device configured with a Remote NDIS driver layer, a datacommunication interface for the portable device, and a virtual networkcoupling the Remote NDIS driver layer and the data communicationinterface. For example, a user with a PDA can download his or herschedule to any other user's desktop PC by simply establishing apoint-to-point communication link between the two devices. The desktopPC does not need to be configured with any specific drivers or interfacecomponents to receive the schedule from the PDA. Furthermore, thepoint-to-point communication link can be a physical USB or 1394connection, or a wireless Bluetooth or infrared connection, or any othersimilar communication protocol that can be utilized for a point-to-pointcommunication link.

Exemplary Point-to-Point Communication Systems

FIG. 5 illustrates a data communication system 500 having componentsthat can be implemented within a computing device, or the components canbe distributed within a computing system having more than one computingdevice. The communication system 500 includes a host computing device502 and a client device 504 communicatively linked with a point-to-pointdata communication link 506. See the description of “Exemplary ComputingSystem and Environment” below for specific examples and implementationsof networks, computing systems, computing devices, and components thatcan be used to implement the invention described herein.

The host computing device 502 and the client device 504 each includemultipoint distributed network data communication components designed toconnect a computing device to a network, such as a LAN, and tocommunicatively link the computing device with remote network-connecteddevices. The host computing device 502 and the client device 504 eachinclude an application layer 508 and 510, respectively. For example, theapplications 508 and 510 can each be a synchronization applicationdesigned to facilitate data communication between the host computingdevice 502 and the client device 504.

Host computing device 502 includes a transport protocol layer 512 thatenables data communication between application layer 508 and other datacommunication layers in the host computing device. The transportprotocol layer 512 can be implemented with the Transmission ControlProtocol/Internet Protocol (TCP/IP) which is a communications protocolthat enables data communication between layers in the host computingdevice 502.

Host computing device 502 also includes an NDIS layer 514, a miniportdriver layer 516, a bus and/or network interface 518, and a Remote NDISlayer 520. The NDIS layer 514 is a network device driver communicationprotocol layer that specifies how the transport protocol layer 512 andthe bus and/or network interface 518 communicate information with eachother. The miniport driver layer 516 communicates information with theNDIS layer 514 and communicates with the bus and/or network interface518. The bus and/or network interface 518 communicates with remotenetwork-connected devices via the Internet 522 through a networkconnection.

Client device 504 includes a transport protocol layer 524, an NDIS layer526, and a virtual miniport driver layer 528. The virtual miniportdriver layer 528 communicates information between the NDIS layer 526 anda Remote NDIS miniport driver layer 530. A virtual LAN 532 communicatesdata between the virtual miniport driver layer 528 and the Remote NDISminiport driver layer 530.

Virtual LAN 532 is defined to appear as a multipoint distributed networkto the Remote NDIS miniport driver layer 530 just as LAN 410 appears tothe Remote NDIS miniport driver layer 416 in FIG. 4. Instead of theRemote NDIS messages being communicated out to the LAN 410 from theRemote NDIS miniport driver layer 416 in FIG. 4, however, Remote NDISmessages from the Remote NDIS miniport driver layer 530 are routed foruse within client device 504 via the virtual LAN 532. Virtual LAN 532 isreferred to as “virtual” because there is no corresponding underlyinghardware used to establish and maintain the communication path betweenthe virtual miniport driver layer 528 and the Remote NDIS miniportdriver layer 530.

The host computing device Remote NDIS layer 520 communicates with NDISlayer 514 and enables the point-to-point communication link 506 betweenhost computing device 502 and client device 504. The Remote NDISminiport driver layer 530 communicates Remote NDIS messages between theRemote NDIS layer 520 and the virtual LAN 532 in client device 504. TheRemote NDIS architecture illustrated in FIG. 5 configures the clientdevice 504 with the Remote NDIS miniport driver layer 530 which enablesthe point-to-point communication link 506 between the host computingdevice 502 and the client device 504.

Host computing device 502 includes a connection interface 534 thatcouples the point-to-point communication link 506 with a connectioninterface 536 at client device 504. The connection interfaces 534 and536 can be implemented as hardware, software, or both to enable aphysical USB or 1394 connection, a wireless Bluetooth or infraredconnection, or any other similar point-to-point communication protocolsupported by the Remote NDIS architecture.

The client device Remote NDIS miniport driver layer 530 communicatesRemote NDIS messages to the virtual LAN 532, which are then communicatedto the virtual miniport driver layer 528. The Remote NDIS messages canbe communicated to the virtual miniport driver layer 528 from the RemoteNDIS miniport driver layer 530 by utilizing medium access controller(MAC) addressing such that the client device 504 passes the Remote NDISmessages to itself from the Remote NDIS miniport driver layer 530 to thevirtual miniport driver layer 528. The virtual miniport driver layer 528is a data communication interface for the particular client device 504and converts the Remote NDIS messages received via the virtual LAN 532to NDIS data packets.

Implementing the host computing device's Remote NDIS miniport driverlayer 530 in an external device (i.e., the client device 504), insteadof in the host computing device 502, facilitates a point-to-pointcommunication link between the two devices without having to configurethe host computing device with interface components to communicate withthe external device. The host computing device 502 can becommunicatively linked with any mobile client device, such as portablelaptop computer, a tablet PC, a handheld PDA, a cellular phone, andsimilar items, without having driver(s) for a particular deviceinstalled on host computing device 502.

Additionally, the Remote NDIS architecture illustrated in FIG. 5facilitates client device 504 utilizing the host computing device 502 asa gateway to the Internet 522 via the point-to-point data communicationlink 506 between the client device 504 and the host computing device502. The point-to-point communication link 506 can be a USB or 1394connection, a Bluetooth wireless connection, or any other similarcommunication protocol supported by the Remote NDIS architecture.

FIG. 6 illustrates a data communication system 600 that includes a hostcomputing device 602 communicatively linked with a first client device604 via a point-to-point data communication link 608 and communicativelylinked with a second client device 606 via a point-to-point datacommunication link 610. Host computing device 602 and client devices 604and 606 each include multipoint distributed network data communicationcomponents designed to connect a computing device to a distributednetwork, and to communicatively link the computing device with remotenetwork-connected devices.

Although not shown, host computing device 602 and client devices 604 and606 can each include an application layer and a transport protocol layerthat enables information communication between the application layer andother communication layers in each respective device. Application andtransport protocol layers are described above with reference to FIG. 5.

Host computing device 602 also includes an NDIS layer 612, a miniportdriver layer 614, a bus and/or network interface 616, and a Remote NDISlayer 618. The miniport driver layer 614 communicates information withthe NDIS layer 612 and communicates with the bus and/or networkinterface 616. The bus and/or network interface 616 communicates withremote network devices connected via the Internet 620 through a networkconnection.

Client devices 604 and 606 each include an NDIS layer 622, a virtualminiport driver layer 624, and a Remote NDIS miniport driver layer 626.A virtual miniport driver layer 624 communicates information between anNDIS layer 622 and a Remote NDIS miniport driver layer 626. A virtualLAN 628 communicates data between the virtual miniport driver layer 624and the Remote NDIS miniport driver layer 626.

The host computing device Remote NDIS layer 618 enables thepoint-to-point data communication link 608 with client device 604 andthe point-to-point data communication link 610 with client device 606.Remote NDIS miniport driver layer 626(1) communicates Remote NDISmessages via virtual LAN 628(1) to the virtual miniport driver layer624(1) in client device 604. Similarly, Remote NDIS miniport driverlayer 626(2) communicates Remote NDIS messages via virtual LAN 628(2) tothe virtual miniport driver layer 624(2) in client device 606.

Data communication system 600 implements the host computing device'sRemote NDIS miniport driver layer 626 in an external device, or devices(i.e., client devices 604 and 606), instead of in the host computingdevice 602. In this example, host computing device 602 can becommunicatively linked with any number of mobile client devices, such asa portable laptop computer, a tablet PC, a handheld PDA, a cellularphone, and similar items, without having driver(s) for a particulardevice installed on host computing device 602.

The point-to-point data communication link 608 between host computingdevice 602 and external client device 604, and the point-to-point datacommunication link 610 between host computing device 602 and externalclient device 606, can be a USB or 1394 connection, a Bluetooth orinfrared wireless connection, or any other similar communicationprotocol supported by the Remote NDIS architecture.

Data communication system 600 also illustrates that multipointdistributed network data communication components can be configured toimplement secure point-to-point data communication links between a hostcomputing device and multiple client devices without actuallyimplementing a multipoint network. For example, host computing device602 can include a first connection interface 630 that couples thepoint-to-point data communication link 608 with a connection interface632 at client device 604, and a second connection interface 634 thatcouples the point-to-point data communication link 610 with a connectioninterface 636 at client device 606. Both client devices 604 and 606 canreceive the same Remote NDIS message from the Remote NDIS layer 618 inhost computing device 602 via an independent point-to-point datacommunication link and without being network connected to the hostcomputing device 602.

Methods for an Exemplary Point-to-Point Communication System

FIG. 7 illustrates a method for implementing a point-to-point datacommunication link between computing devices with multipoint distributednetwork data communication components, and communicating data between ahost device and a client device. The order in which the method isdescribed is not intended to be construed as a limitation. Furthermore,the method can be implemented in any suitable hardware, software,firmware, or combination thereof.

At block 700, a network communication component designed for datacommunication over a distributed network is provided. For example, adata communication interface driver is provided with a client devicesuch as the Remote NDIS miniport driver layer 530 (FIG. 5). The datacommunication interface driver is configured to communicatively linkwith a data communication interface of a host computing device via apoint-to-point data communication link. For example, the Remote NDISminiport driver layer 530 is communicatively linked with the Remote NDIScomponent 520 at host computing device 502 via the point-to-pointcommunication link 506.

At block 702, a connection interface is provided to couple the networkcommunication component with a remote host computing device. Forexample, connection interface 536 couples the point-to-pointcommunication link 506 with client device 504. The connection interfacecan be implemented as hardware, software, or both to enable a physicalUSB or 1394 connection, a wireless Bluetooth or infrared connection, orany other similar point-to-point communication protocol supported by thedata communication interface (e.g., the Remote NDIS architecture).

At block 704, a virtual network is provided to communicatively link thenetwork communication component and a virtual driver component of aclient computing device. For example, virtual LAN 532 communicativelylinks the Remote NDIS miniport driver layer 530 and the virtual miniportdriver layer 528 at client device 504.

At block 706, the client device connection interface is coupled to thehost device to establish the point-to-point data communication link.Alternatively, at block 708, a second client device connection interfaceis coupled to the host device to establish a second point-to-point datacommunication link. For example, connection interface 636 (FIG. 6)couples a second client device 606 to host computing device 602 via asecond point-to-point data communication link 610.

At block 710, data is received from the remotely located datacommunication interface. For example, Remote NDIS messages are receivedfrom the Remote NDIS component 520 at host computing device 502 via thepoint-to-point data communication link 506 and connection interface 536.Additionally, for the second client device, the Remote NDIS messages arereceived from the Remote NDIS component 520 at host computing device 502via the second point-to-point data communication link and second clientdevice connection interface.

At block 712, the data is communicated from the data communicationinterface driver (i.e., the network communication component) to avirtual driver component for the client device via a virtual network.For example, the Remote NDIS messages are received at the Remote NDISminiport driver layer 530 and communicated to the virtual miniportdriver layer 528 via virtual LAN 532.

Exemplary Computing System and Environment

FIG. 8 illustrates an example of a computing environment 800 withinwhich the computer, network, and system architectures described hereincan be either fully or partially implemented. Exemplary computingenvironment 800 is only one example of a computing system and is notintended to suggest any limitation as to the scope of use orfunctionality of the network architectures. Neither should the computingenvironment 800 be interpreted as having any dependency or requirementrelating to any one or combination of components illustrated in theexemplary computing environment 800.

The computer and network architectures can be implemented with numerousother general purpose or special purpose computing system environmentsor configurations. Examples of well known computing systems,environments, and/or configurations that may be suitable for useinclude, but are not limited to, personal computers, server computers,thin clients, thick clients, hand-held or laptop devices, multiprocessorsystems, microprocessor-based systems, set top boxes, programmableconsumer electronics, network PCs, minicomputers, mainframe computers,gaming consoles, distributed computing environments that include any ofthe above systems or devices, and the like.

Implementing a point-to-point data communication link with multipointdistributed network data communication components may be described inthe general context of computer-executable instructions, such as programmodules, being executed by a computer. Generally, program modulesinclude routines, programs, objects, components, data structures, etc.that perform particular tasks or implement particular abstract datatypes. Implementing a point-to-point data communication link withmultipoint distributed network data communication components may also bepracticed in distributed computing environments where tasks areperformed by remote processing devices that are linked through acommunications network. In a distributed computing environment, programmodules may be located in both local and remote computer storage mediaincluding memory storage devices.

The computing environment 800 includes a general-purpose computingsystem in the form of a computer 802. The components of computer 802 caninclude, by are not limited to, one or more processors or processingunits 804, a system memory 806, and a system bus 808 that couplesvarious system components including the processor 804 to the systemmemory 806.

The system bus 808 represents one or more of any of several types of busstructures, including a memory bus or memory controller, a peripheralbus, an accelerated graphics port, and a processor or local bus usingany of a variety of bus architectures. By way of example, sucharchitectures can include an Industry Standard Architecture (ISA) bus, aMicro Channel Architecture (MCA) bus, an Enhanced ISA (EISA) bus, aVideo Electronics Standards Association (VESA) local bus, and aPeripheral Component Interconnects (PCI) bus also known as a Mezzaninebus.

Computer system 802 typically includes a variety of computer readablemedia. Such media can be any available media that is accessible bycomputer 802 and includes both volatile and non-volatile media,removable and non-removable media. The system memory 806 includescomputer readable media in the form of volatile memory, such as randomaccess memory (RAM) 810, and/or non-volatile memory, such as read onlymemory (ROM) 812. A basic input/output system (BIOS) 814, containing thebasic routines that help to transfer information between elements withincomputer 802, such as during start-up, is stored in ROM 812. RAM 810typically contains data and/or program modules that are immediatelyaccessible to and/or presently operated on by the processing unit 804.

Computer 802 can also include other removable/non-removable,volatile/non-volatile computer storage media. By way of example, FIG. 8illustrates a hard disk drive 816 for reading from and writing to anon-removable, non-volatile magnetic media (not shown), a magnetic diskdrive 818 for reading from and writing to a removable, non-volatilemagnetic disk 820 (e.g., a “floppy disk”), and an optical disk drive 822for reading from and/or writing to a removable, non-volatile opticaldisk 824 such as a CD-ROM, DVD-ROM, or other optical media. The harddisk drive 816, magnetic disk drive 818, and optical disk drive 822 areeach connected to the system bus 808 by one or more data mediainterfaces 826. Alternatively, the hard disk drive 816, magnetic diskdrive 818, and optical disk drive 822 can be connected to the system bus808 by a SCSI interface (not shown).

The disk drives and their associated computer-readable media providenon-volatile storage of computer readable instructions, data structures,program modules, and other data for computer 802. Although the exampleillustrates a hard disk 816, a removable magnetic disk 820, and aremovable optical disk 824, it is to be appreciated that other types ofcomputer readable media which can store data that is accessible by acomputer, such as magnetic cassettes or other magnetic storage devices,flash memory cards, CD-ROM, digital versatile disks (DVD) or otheroptical storage, random access memories (RAM), read only memories (ROM),electrically erasable programmable read-only memory (EEPROM), and thelike, can also be utilized to implement the exemplary computing systemand environment.

Any number of program modules can be stored on the hard disk 816,magnetic disk 820, optical disk 824, ROM 812, and/or RAM 810, includingby way of example, an operating system 826, one or more applicationprograms 828, other program modules 830, and program data 832. Each ofsuch operating system 826, one or more application programs 828, otherprogram modules 830, and program data 832 (or some combination thereof)may include an embodiment of a point-to-point data communication linkimplemented with multipoint distributed network data communicationcomponents.

Computer system 802 can include a variety of computer readable mediaidentified as communication media. Communication media typicallyembodies computer readable instructions, data structures, programmodules, or other data in a modulated data signal such as a carrier waveor other transport mechanism and includes any information deliverymedia. The term “modulated data signal” means a signal that has one ormore of its characteristics set or changed in such a manner as to encodeinformation in the signal. By way of example, and not limitation,communication media includes wired media such as a wired network ordirect-wired connection, and wireless media such as acoustic, RF,infrared, and other wireless media. Combinations of any of the above arealso included within the scope of computer readable media.

A user can enter commands and information into computer system 802 viainput devices such as a keyboard 834 and a pointing device 836 (e.g., a“mouse”). Other input devices 838 (not shown specifically) may include amicrophone, joystick, game pad, satellite dish, serial port, scanner,and/or the like. These and other input devices are connected to theprocessing unit 804 via input/output interfaces 840 that are coupled tothe system bus 808, but may be connected by other interface and busstructures, such as a parallel port, game port, or a universal serialbus (USB).

A monitor 842 or other type of display device can also be connected tothe system bus 808 via an interface, such as a video adapter 844. Inaddition to the monitor 842, other output peripheral devices can includecomponents such as speakers (not shown) and a printer 846 which can beconnected to computer 802 via the input/output interfaces 840.

Computer 802 can operate in a networked environment using logicalconnections to one or more remote computers, such as a remote computingdevice 848. By way of example, the remote computing device 848 can be apersonal computer, portable computer, a server, a router, a networkcomputer, a peer device or other common network node, and the like. Theremote computing device 848 is illustrated as a portable computer thatcan include many or all of the elements and features described hereinrelative to computer system 802.

Logical connections between computer 802 and the remote computer 848 aredepicted as a local area network (LAN) 850 and a general wide areanetwork (WAN) 852. Such networking environments are commonplace inoffices, enterprise-wide computer networks, intranets, and the Internet.When implemented in a LAN networking environment, the computer 802 isconnected to a local network 850 via a network interface or adapter 854.When implemented in a WAN networking environment, the computer 802typically includes a modem 856 or other means for establishingcommunications over the wide network 852. The modem 856, which can beinternal or external to computer 802, can be connected to the system bus808 via the input/output interfaces 840 or other appropriate mechanisms.It is to be appreciated that the illustrated network connections areexemplary and that other means of establishing communication link(s)between the computers 802 and 848 can be employed.

In a networked environment, such as that illustrated with computingenvironment 800, program modules depicted relative to the computer 802,or portions thereof, may be stored in a remote memory storage device. Byway of example, remote application programs 858 reside on a memorydevice of remote computer 848. For purposes of illustration, applicationprograms and other executable program components, such as the operatingsystem, are illustrated herein as discrete blocks, although it isrecognized that such programs and components reside at various times indifferent storage components of the computer system 802, and areexecuted by the data processor(s) of the computer.

Conclusion

Technological advances have enabled better and more adaptable networkingcomponents and devices to meet the needs of consumers requiringsophisticated networking solutions. The systems and methods describedherein provide a versatile point-to-point data communication techniquethat can be implemented with the distributed networking componentsdesigned for multipoint data communications.

Although the systems and methods have been described in languagespecific to structural features and/or methodological steps, it is to beunderstood that the invention defined in the appended claims is notnecessarily limited to the specific features or steps described. Rather,the specific features and steps are disclosed as preferred forms ofimplementing the claimed invention.

1. A data communication system configured to communicatively link a hostdevice and a remote client device with a point to-point datacommunication link, the host device and the remote client device eachconfigured for multipoint data communication over a distributed network,the data communication system comprising: a Remote Network DriverInterface Specification (NDIS) driver of the host device implemented inthe remote client device, the Remote NDIS driver configured tocommunicatively link with a data Remote NDIS communication interface ofthe host device via the point-to-point data communication link; avirtual driver component configured to communicate with the Remote NDISdriver and the remote client device; and a virtual network configured tocommunicatively link the Remote NDIS driver and the virtual drivercomponent in the remote client device.
 2. A data communication system asrecited in claim 1, wherein Remote NDIS communication interface isconfigured to communicate Remote NDIS messages with the Remote NDISdriver via the point-to-point data communication link.
 3. A datacommunication system as recited in claim 1, wherein the virtual networkis a local area network.
 4. A data communication system as recited inclaim 1, wherein the Remote NDIS driver is further configured tocommunicate with the virtual driver component via the virtual network.5. A data communication system as recited in claim 1, wherein the RemoteNDIS driver is further configured to communicate Remote NDIS messageswith the virtual driver component via the virtual network.
 6. A datacommunication system as recited in claim 1, wherein the Remote NDIScommunication interface is further configured to communicate with theRemote NDIS driver via the point-to-point data communication link, andthe Remote NDIS driver is further configured to communicate with thevirtual driver component via the virtual network.
 7. A datacommunication system as recited in claim 1, wherein the Remote NDIScommunication interface is further configured to communicate Remote NDISmessages with the Remote NDIS driver via the point-to-point datacommunication link, and the Remote NDIS driver is further configured tocommunicate the Remote NDIS messages with the virtual driver componentvia the virtual network.
 8. A data communication system as recited inclaim 1, further comprising a connection interface configured to couplethe point-to-point data communication link with the remote clientdevice.
 9. A data communication system as recited in claim 1, furthercomprising a Universal Serial Bus data communication interfaceconfigured to couple the point-to-point data communication link with theremote client device.
 10. A data communication system as recited inclaim 1, further comprising a 1394 bus data communication interfaceconfigured to couple the point-to-point data communication link with theremote client device.
 11. A data communication system as recited inclaim 1, further comprising a wireless data communication interfaceconfigured to couple the point-to-point data communication link with theremote client device.
 12. A data communication system as recited inclaim 1, further comprising a Bluetooth data communication interfaceconfigured to couple the point-to-point data communication link with theremote client device.
 13. A data communication system as recited inclaim 1, further comprising an infrared data communication interfaceconfigured to couple the point-to-point data communication link with theremote client device.
 14. A method for implementing a point to pointdata communication link between computing devices, the methodcomprising: implementing a Remote Network Driver Interface Specification(NDIS) driver of a host computing device in a remote client computingdevice, the Remote NDIS driver designed for data communication over adistributed network and configured to communicatively link with a RemoteNDIS component of the host computing device via the point-to-point datacommunication link; implementing a connection interface to couple theRemote NDIS driver with the host computing device; and implementing avirtual network to communicatively link the Remote NDIS driver and avirtual driver component of the remote client computing device.
 15. Amethod as recited in claim 14, wherein implementing the Remote NDISdriver includes implementing a data communication interface driver tocommunicatively link with a data communication interface of the hostcomputing device via the point-to-point data communication link.
 16. Amethod as recited in claim 14, wherein implementing the Remote NDISdriver includes implementing the Remote NDIS driver to communicateRemote NDIS messages with the Remote NDIS component of the hostcomputing device via the point-to-point data communication link.
 17. Amethod as recited in claim 14, wherein implementing the connectioninterface includes providing a point-to-point data communicationprotocol interface.
 18. A method as recited in claim 14, whereinimplementing the connection interface includes providing a UniversalSerial Bus data communication interface.
 19. A method as recited inclaim 14, wherein implementing the connection interface includesproviding a 1394 bus data communication interface.
 20. A method asrecited in claim 14, wherein implementing the connection interfaceincludes providing a wireless data communication interface.
 21. A methodas recited in claim 14, wherein implementing the connection interfaceincludes providing a Bluetooth data communication interface.
 22. Amethod as recited in claim 14, wherein implementing the connectioninterface includes providing an infrared data communication interface.23. A method as recited in claim 14, wherein implementing the virtualnetwork includes providing a virtual local area network.
 24. A method asrecited in claim 14, wherein implementing the virtual network includesproviding a virtual local area network to communicate Remote NDISmessages between the Remote NDIS driver and the virtual drivercomponent.
 25. A method as recited in claim 14, wherein implementing theRemote NDIS driver includes implementing the Remote NDIS driver tocommunicate Remote NDIS messages with the Remote NDIS component of thehost computing device via the point-to-point data communication link,and wherein implementing the virtual network includes implementing avirtual local area network to communicate the Remote NDIS messagesbetween the Remote NDIS driver and the virtual driver component.